Segfaults on trying to add an SSO account.

Thread 1 ".seafile-applet" hit Breakpoint 1.12, QMessageLogger::fatal (this=this@entry=0x7ffffffec9f0, 
    msg=msg@entry=0x7fffe5d1f0c8 "Cannot mix incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)")
    at /build/qtbase-everywhere-src-6.9.2/src/corelib/global/qlogging.cpp:879

edit: backtrace at https://gist.github.com/melvyn2/152ea59cd32804f7a189699fff988d09

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 442070 --extra-nixpkgs-config '{ }'
Commit: e9d2ecdae1711d7d035ed64dca74dbf2ea0d389c

x86_64-linux

Segfaults on trying to add an SSO account.

Thread 1 ".seafile-applet" hit Breakpoint 1.12, QMessageLogger::fatal (this=this@entry=0x7ffffffec9f0, 
    msg=msg@entry=0x7fffe5d1f0c8 "Cannot mix incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)")
    at /build/qtbase-everywhere-src-6.9.2/src/corelib/global/qlogging.cpp:879

edit: backtrace at https://gist.github.com/melvyn2/152ea59cd32804f7a189699fff988d09

Will try updating nixos to see if that's why it's pulling in an old qtsvg

yeah i just found the old qtsvg as well in your backtrace

Ok looks like it worked once I updated my install to latest unstable. I'm not sure how my system qtsvg library leaked into the client - it feels like that shouldn't be happening. It looks like it was loading the system breeze theme which was pulling in the versions it was built with. Regardless, this was not a user facing issue.

the correct qtsvg version is being prepended to the qt variables in the wrapper, perhaps some plugin pulled it in?

It seems the maintainer has recently dropped maintaining the server and module, i assume they also do not really maintain the client. I'll merge this without waiting 👍